1. |
CRM Evaluation Center
Nov 23, 2009
Today's usage of Decision Support Systems (DSS), combined with vetted CRM knowledge bases, allows organizations to save time and money, achieving better and more reliable/fully-documented decisions, a quantum improvement over the widely-used subjective process of selecting complex enterprise software...
|
| 2. |
CRM RFP Template (1 Page)
by TEC Staff
Nov 22, 2007
Abstract : Don't let your CRM software selection become a risky venture. Play your cards right and use a CRM RFP template. Find out what a CRM RFP template is and how it can save you time and money. We also tell you how you can write your own CRM RFP template, so you can get the CRM solution you need for your enterprise. Don't place any bets until you have all the information you need about how you can make a CRM RFP work for you.
|
| 3. |
How Many Napkins Have to Die Needlessly? A Case for Business Architecture ( Pages)
by J. Dowling
Apr 5, 2000
Abstract : Architecture is a description of how things go together. Once we know what our Business Architecture is, we can design an Information Technology Architecture to compliment it. Without a clearly stated architecture, there is a good chance that things will be put together wrong.
|
| 4. |
Customer Relationship Management (CRM) - CRM Acronym Definition and Related White Papers ( Pages)
by TEC Staff
Jun 13, 2009
Abstract : Customer Relationship Management (CRM) systems are software systems that cover the range of interaction a company has with its current, or potential customers. Its functionality can include marketing automation, sales force automation, help desk, customer service and support, partner management, contract management and creation, project and team management, Internet sales, e-mail response management, analytics, and important technical criteria.
|
| 5. |
Architecture–Centered Information Systems In The Manufacturing Domain – Part V – Applying the Methodology (11 Pages)
by Glen B. Alleman
Aug 23, 2000
Abstract : Architecture bridges the semantic gap between the requirements and software. Application software systems must be architected in order to deal with the current and future needs of the business organization. Managing software projects using architecture–centered methodologies must be an intentional step in the process of deploying information systems – not an accidental by–product of the software acquisition and integration process. Part V – Applying the Methodology.
|
| 6. |
Scala and Microsoft Become (Not So) Strange CRM Bedfellows Part Two: Market Impact Continued ( Pages)
by P.J. Jakovljevic
Aug 29, 2003
Abstract : Microsoft's foray into the CRM arena has not been a bed of roses, despite its indisputably large marketing muscle and R&D investment, its strong channel, traditionally attractive pricing policies, and the aura and experience within the market segment. Microsoft CRM remains both a threat and an opportunity for the most nimble mid-market CRM vendors. Microsoft’s entry with CRM evangelism through an array of seminars nationwide has bolstered the market’s awareness of the need for CRM applications.
|
| 7. |
Applying the Power of Social Networks to Customer Relationship Management ( Pages)
by Wayne Thompson
Sep 19, 2007
Abstract : Customer relationship management (CRM) is rapidly morphing from a customer management model to one of customer engagement. Social networks, podcasts, blogs, and wikis are enabling customers to become advocates, and not simply the targets they were in the traditional CRM process. The same techniques are also being used within the CRM industry itself to create a content-rich, social media environment for CRM professionals. Find out what these sweeping changes mean to businesses and CRM professionals alike, as TEC's director of research Wayne Thompson sits down with Paul Greenberg and Bruce Culbert of BPT Partners, a leading CRM consulting firm.
|
| 8. |
Architecture-Centered Information Systems In The Manufacturing Domain - Part II - The Architecture Process ( Pages)
by Glen B. Alleman
Sep 6, 2002
Abstract : Architecture bridges the semantic gap between the requirements and software. Application software systems must be architected in order to deal with the current and future needs of the business organization. Managing software projects using architecture-centered methodologies must be an intentional step in the process of deploying information systems ― not an accidental by-product of the software acquisition and integration process.
|
| 9. |
Architecture-Centered Information Systems In The Manufacturing Domain - Part I - Introduction to Software Architecture ( Pages)
by Glen B. Alleman
Sep 4, 2002
Abstract : Architecture bridges the semantic gap between the requirements and software. Application software systems must be architected in order to deal with the current and future needs of the business organization. Managing software projects using architecture-centered methodologies must be an intentional step in the process of deploying information systems ― not an accidental by-product of the software acquisition and integration process.
|
| 10. |
Architecture-Centered Information Systems In The Manufacturing Domain - Part III - Steps in the Architecture Process ( Pages)
by Glen B. Alleman
Sep 11, 2002
Abstract : Architecture bridges the semantic gap between the requirements and software. Application software systems must be architected in order to deal with the current and future needs of the business organization. Managing software projects using architecture–centered methodologies must be an intentional step in the process of deploying information systems – not an accidental by–product of the software acquisition and integration process.
|
CART 
